General Information Information on the transmitted data. Business unit Location of a branch office. Place/ Location code UN/Locode; e.g. the location of the user's branch office. Location name. If there is no UN/LoCode available for this place, alternatively the name can be set. carrier code according to DAKOSY key directory carrier code (Reedercodes) carrier position position of the goods within the original order of the carrier mandatory if form type = L18 Communication information. Contains information on sender, recipients and creation time. Communication participants Up to 11 entries can be sent: SENDER - mandatory with DAKOSY-code EDI_PROVIDER - optional; 'DAKOSY', if message should be processed by DAKOSY RECIPIENT - mandatory with DAKOSY-Code. Maximum of nine entries is possible. Date and time of message creation. container length required if sign empty/full = E - according to HABIS code directory A18 container height height of the container according to HABIS code directory A19 container type required if sign empty/full = E - according to HABIS code directory A05 ISO-code container ISO-code container construction A = aluminium, S = steel P = plywood combinations of more than one type of material are possible. container distinguishing characteristics R = individual ocean carrier L = leasing or R/L date of discharge Format: YYYYMMDD time of discharge Format: HH:MM mandatory if form type = C18 dispatcher name of the dispatcher telphone number of the dispatcher container prefix listing of multiple prefixes is only allowed for empty containers container number from lowers bounds of a number range for empty containers listing of multiple serial numbers is only allowed for empty containers container number to upper bounds of a number range for empty containers listing of multiple serial numbers is only allowed for empty containers General Message definition Describes the contents of a message (metainfo and data) User information Information on the user who sent the message. Metainfo Contains information concerning transaction type, communication parties etc. Transaction type Specifies the transaction type (GM01, AB01 etc.). Only one transaction per file is allowed. Different types must be sent in separate files. Application name Name of the application served by the interface. E.g. SEEDOS, ATLAS Testflag 0 - false (default); 1- true; transmission for test purpose Number of messages Number of messages (elements) that are collected in the transmitted file. ocean carrier code code has to be agrred upon between the quay operator and the liner agent abbreviation of the ocean carrier abbriviated name of the ocean carrier depot/stock field indicates from which of the ocean carriers stocks the container should be taken from DAKOSY-code 4-letter code identifying the participant application usage Alias code. Describes how the participant is identified in another system, e.g. DAK as DAKOSY-code. Other identifiers are not specified yet. participant name just for informal use Password Needs only to be set if required by the specified role. SENDER RECIPIENT EDI_PROVIDER position container position number of containers only if sign empty/full = E sign empty/full E = empty F = full container number required if sign empty/full = F format: bytes content 1 - 4 Prefix 5 - 12 Number indicator rented container Y = yes N = no indicator damaged Y = yes N = no CSC-permit maximum gross weight weight in tons indicator lowest tara weight Y = yes N = no indicator acceptation of customs bond Y = yes N = no comments indicator liability certificate by choosing J the gate-pass will be replaced if the container is full Y = yes N = no official seal number (e.g. customs seal) only if sign empty/full = F markings only for loose cargo if form type = L18 (release) automatic processing the customer can a number of automatic processing features for the transport order rcv = automatic receiving fwd = automatic forwarding (requires automatic receiving) qst = automatic retrieval of the quay status (requires a specification of the loading /discharge location) cfd = automatic forwarding depending on a positive quay status (requires automatic receiving and retrieval of the quay status) loading location according to HABIS code directory A07 final destination/ train station final destination/ train station of the container date of the release Format: YYYYMMDD port code UN/LOCODE mode of transport R = rail, T = truck, F = feeder operator name of the truck/ feeder/ railway operator order reference reference of the transport order comments form type C18 = container L18 = loose cargo B/L-number bill of lading number according to the manifest mandatory if form type = L18 warehouse number according to DAKOSY key directory warehouse number code (Schuppencode) type of reference used Release version of the message / message element ascending sequence (not necassarily continuous) starting with version 01 (new transport order etc) - all versions above 01 are interpreted as a revision of previously communicated data ships name code IATA-code / callsign of the vessel ship name eta-date Format: YYYYMMDD voyage number mandatory if form type = L18 Transaction name Release Message provider name of the party who is responsible for the underlying scheme. Version of message definition Message type Code defined by the provider for the specified transaction, e.g. GM01 = customs declaration AC02 = transport order Transaction information Phone number plain text without validation. Either phone number or e-mail address must be filled if the user-element is transmitted.